You update a Microsoft SQL Server table by using SAS/ACCESS^® Interface to Microsoft SQL Server and the SQL procedure. You then see a note in the log that confirms that the row was updated. However, the data in the row is not updated. There is no indication that the update did not work as expected. In some cases, the update does complete successfully.

This issue is caused by the underlying DataDirect driver. SAS is working with Progress to resolve the issue.

The issue occurs when all of the following are true:

• The Microsoft SQL Server version is 2016 or later.
• The column in the database has a DATETIME definition.
• The SQLSVR LIBNAME engine is used.
• The CURSOR_TYPE=DYNAMIC option is not in the LIBNAME statement.

In the meantime, you can use one of the following workarounds:

• Set EnableScrollableCursors=4 in the obdc.ini file. Then add the CURSOR_TYPE=DYNAMIC option to the LIBNAME statement.
• Use the SQL pass-through facility.
• Change the data type in the SQL Server table from DATETIME to DATETIME2.
• Change the Compatibility Level setting of the SQL Server database to SQL Server 2014 (120). This setting is database-specific, so it would need to be done only for the database that the data server is accessing.
• Migrate the database by using the SQL Server Native Client driver. Deselect the advanced option Map MSS Datetime Type in the OpenEdge DB to SQL Server Utility in order to migrate OpenEdge DATETIME types to Microsoft SQL Server DATETIME2 types.

Operating System and Release Information

A fix for this issue for DataDirect ODBC Driver for Amazon Redshift 9.43 is available at:

A fix for this issue for DataDirect ODBC Driver for Greenplum 9.43 is available at:

A fix for this issue for DataDirect ODBC Driver for Microsoft SQL Server 9.43 is available at: